-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Backport/7.x/yaml test runner #4179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* stage, now actually sends querystring parameters * DynamicResponse now useful in the context of yaml runner * support _arbitrary_key_ * more assertions * more assertions * more assertions * gh workflow, some changes to allow client url to be passed on commandlie * update workflow * update docker image ref * update docker image ref * update health checks * attach for visibility * --no-healthcheck not valid with -a * no health check * add limits * explicit hostname * single node discovery * minimize options * wrong .NET sdk * dotnet-run should have been dotnet run * need -- to separate args * actions/setup-dotnet#29 :sadpanda: * print some info to assert container information * cleaned up program a bit now discovers revision to download from running elasticsearch version * junit xml exporter * can now pass in output file as arg, report totals on stdout * export to artifacts * yaml * yaml spacing * make sure build/output exists * always upload artifact * test out logging commands * update es container config * reenable ES_JAVA_OPTS * java opts not able to set to 1g enable memory_lock * drop single-node discovery-type * back to single node * stage * .jenkins build * update our .jenkins folder * update runner to pretty print failures * move from .jenkins folder to .ci * add readme to the .ci folder * attempt to show logs in github actions * disable github actions for now * regenerate code after rebase * unit test for __arbitrary_key__ used the wrong meaning * Add PowerShell scripts to run on Windows This commit adds Powershell script equivalents of the ci shell scripts, to allow yaml tests to run on Windows with Docker * added --profile switch to yaml runner that waits before running the tests and prints the PID * update ci jobs go-elasticsearch references * Update src/Elasticsearch.Net/Responses/Dynamic/DynamicDictionary.cs Co-Authored-By: Russ Cam <russ.cam@elastic.co> * only automatically set proxy on client if we see mitmproxy running * Update src/Tests/Tests.YamlRunner/DoMapper.fs Co-Authored-By: Russ Cam <russ.cam@elastic.co> * Update .ci/run-tests Co-Authored-By: Russ Cam <russ.cam@elastic.co> * Addressed various PR feedback (cherry picked from commit c3f85a0)
russcam
pushed a commit
that referenced
this pull request
Nov 15, 2019
* Rest API Spec tests runner (#4123) * stage, now actually sends querystring parameters * DynamicResponse now useful in the context of yaml runner * support _arbitrary_key_ * more assertions * more assertions * more assertions * gh workflow, some changes to allow client url to be passed on commandlie * update workflow * update docker image ref * update docker image ref * update health checks * attach for visibility * --no-healthcheck not valid with -a * no health check * add limits * explicit hostname * single node discovery * minimize options * wrong .NET sdk * dotnet-run should have been dotnet run * need -- to separate args * actions/setup-dotnet#29 :sadpanda: * print some info to assert container information * cleaned up program a bit now discovers revision to download from running elasticsearch version * junit xml exporter * can now pass in output file as arg, report totals on stdout * export to artifacts * yaml * yaml spacing * make sure build/output exists * always upload artifact * test out logging commands * update es container config * reenable ES_JAVA_OPTS * java opts not able to set to 1g enable memory_lock * drop single-node discovery-type * back to single node * stage * .jenkins build * update our .jenkins folder * update runner to pretty print failures * move from .jenkins folder to .ci * add readme to the .ci folder * attempt to show logs in github actions * disable github actions for now * regenerate code after rebase * unit test for __arbitrary_key__ used the wrong meaning * Add PowerShell scripts to run on Windows This commit adds Powershell script equivalents of the ci shell scripts, to allow yaml tests to run on Windows with Docker * added --profile switch to yaml runner that waits before running the tests and prints the PID * update ci jobs go-elasticsearch references * Update src/Elasticsearch.Net/Responses/Dynamic/DynamicDictionary.cs Co-Authored-By: Russ Cam <russ.cam@elastic.co> * only automatically set proxy on client if we see mitmproxy running * Update src/Tests/Tests.YamlRunner/DoMapper.fs Co-Authored-By: Russ Cam <russ.cam@elastic.co> * Update .ci/run-tests Co-Authored-By: Russ Cam <russ.cam@elastic.co> * Addressed various PR feedback (cherry picked from commit c3f85a0) * move to 7. snapshot * clean up sln * DynamicDictionary Get should deal with nullables * update jenkins build scripts to latest * Add support for Get<DynamicDictionary>() on DynamicDictionary * Add more debug assertions around flakey test (cherry picked from commit 655b5ce)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.